Hello,
Your modifications can work with .net Core 2.0?
If Yes, How can I use it ?

Vincent.

Hello Vincent,
I forked Alan's repository and my changes can be found here. The component was recompiled as a separate project and It's compatible with .NET Core 2. I am currently using it on my project. Unfortunately it is not yet available as a Nuget package since Alan is the owner of the project. You would need to either download a copy and reference the project from your solution or compile it and reference the generated DLL.

I have additional changes that I haven't uploaded yet. The most remarkable one is the support for areas and the possibility to having multiple instances of the ReportController (with different names) which is not currently supported on the other version of the component.

If there is interest from the community, I can add these changes as well.

Carlos

Carlos,

I have used your version of the reportviewer for core 2.0.
It worked intermittently with an Area setup.
I had a controller called ReportController in Controllers folder.
I had same controller in Area called ServerApps.
So Report/MyReport and ServerApps/Report/MyReport would both work.
I found that removing the Reports controller from the typical controllers folder and leaving
the area one remaining, the area report failed to load.
Ideally I wanted to the area report as opposed to the typical controller.
Therefore, I would be very interested if you have fixed this scenario and you could post the solution.
If not, then I guess I will have to remove the area.

Regards,

Wayne

Hello Wayne,
I haven't looked at the issue you are describing. I am working on some other issues that I identified on the report component. I will take a look at this and I will update the repository as soon as I can, I need to meet a deadline on my current assignment.

Thanks for the input, Wayne,
Carlos

Hey, have you plans to update also for .net core 3 ?

Hello, has anyone tried using this with .NET Core 3.1 or higher?